-
Notifications
You must be signed in to change notification settings - Fork 16.7k
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
I've signed the CLA in the meantime. |
Should obsolete #2779 |
I've based some parts of the README from PR above though. |
I've mentioned Kubernetes 1.7+, but since I'm using quite recent api versions, maybe 1.9+ is more suited? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things:
incubator
has been somewhat deprecated,stable
is a good place to start- kubernetes 1.9+
- provisioner name probably should be empty by default, since afaik there is no "standard" for this
Updated point 1 and 2. About 3. I feel like a 'default' is needed, so I took a look at nfs-server-provisioner. They do it as follows:
But i do not like the 'cluster.local/' prefix. I don't have a single cluster named 'cluster.local' for example so we shouldn't assume that's the name. Afaik there is no way to get the cluster name through Helm. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
What are the checks that are holding this patch up? Not sure how to read e2e CI and tide results |
@kingdonb Waiting on an approval - @unguiculus - can you take a quick peek? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more things:
- Change
incubator
references tostable
- Add
heritage
labels - Apply our RBAC best practices: https://github.com/kubernetes/helm/blob/master/docs/chart_best_practices/rbac.md
@@ -0,0 +1,42 @@ | |||
apiVersion: apps/v1beta2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apps/v1
Implemented all remarks, and fixed a storageClass issue while i was at it. :-) |
/assign @mattfarina |
/retest pull-charts-e2e |
/lgtm |
@unguiculus @prydonius |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidkarlsen, unguiculus, verwilst The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Add nfs-client-provisioner chart * Moved to stable, minimum version is 1.9+ * Change provisionerName default * Change incubator references to stable in README, Add heritage labels, apply RBAC best practices, apps/v1 * update values.yaml to serviceAccount changes * use helpers for storageclass provisionerName * actually use template for helper variable * Make allowVolumeExpansion and reclaimPolicy configurable * fullname everywhere, update readme and set to latest version * use helper for serviceAccountName * Update deployment.yaml * Update values.yaml * remove whitespace * use helper function for sa binding as well * add default nfs.server value for ci * add endpoints bindings * go to version 3.0.1 * add archiveOnDelete, sync clusterrole rules * fix README.md parameters Signed-off-by: Marek Bartik <[email protected]> Signed-off-by: Marek Bartik <[email protected]>
* Add nfs-client-provisioner chart * Moved to stable, minimum version is 1.9+ * Change provisionerName default * Change incubator references to stable in README, Add heritage labels, apply RBAC best practices, apps/v1 * update values.yaml to serviceAccount changes * use helpers for storageclass provisionerName * actually use template for helper variable * Make allowVolumeExpansion and reclaimPolicy configurable * fullname everywhere, update readme and set to latest version * use helper for serviceAccountName * Update deployment.yaml * Update values.yaml * remove whitespace * use helper function for sa binding as well * add default nfs.server value for ci * add endpoints bindings * go to version 3.0.1 * add archiveOnDelete, sync clusterrole rules * fix README.md parameters Signed-off-by: aba182 <[email protected]>
* Add nfs-client-provisioner chart * Moved to stable, minimum version is 1.9+ * Change provisionerName default * Change incubator references to stable in README, Add heritage labels, apply RBAC best practices, apps/v1 * update values.yaml to serviceAccount changes * use helpers for storageclass provisionerName * actually use template for helper variable * Make allowVolumeExpansion and reclaimPolicy configurable * fullname everywhere, update readme and set to latest version * use helper for serviceAccountName * Update deployment.yaml * Update values.yaml * remove whitespace * use helper function for sa binding as well * add default nfs.server value for ci * add endpoints bindings * go to version 3.0.1 * add archiveOnDelete, sync clusterrole rules * fix README.md parameters Signed-off-by: aba182 <[email protected]>
* Add nfs-client-provisioner chart * Moved to stable, minimum version is 1.9+ * Change provisionerName default * Change incubator references to stable in README, Add heritage labels, apply RBAC best practices, apps/v1 * update values.yaml to serviceAccount changes * use helpers for storageclass provisionerName * actually use template for helper variable * Make allowVolumeExpansion and reclaimPolicy configurable * fullname everywhere, update readme and set to latest version * use helper for serviceAccountName * Update deployment.yaml * Update values.yaml * remove whitespace * use helper function for sa binding as well * add default nfs.server value for ci * add endpoints bindings * go to version 3.0.1 * add archiveOnDelete, sync clusterrole rules * fix README.md parameters Signed-off-by: Jakob Niggel <[email protected]>
What this PR does / why we need it:
Adds nfs-client-provisioner chart
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer: